Completeness of optional attributes

Characteristic Name:	Completeness of optional attributes
Dimension:	Completeness
Description:	Optional attributes should not contain invalid null values
Granularity:	Element
Implementation Type:	Rule-based approach
Characteristic Type:	Declarative

Verification Metric:

The number of invalid null values reported in an optional attribute per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Provide default values for each valid case of null values for the attribute in concern so that null values occur only for actually missing values which are invalid cases for the attribute in concern.	Case1: Attribute values that are not defined for a particular entity instance (e.g.: Maiden name of unmarried women ) Such instances will get the default value “NOT DEFINED” Case2 : Attribute values that are defined for the entity instance whereas the real value for the attribute instance is null (eg: Vehicle number of a student who does not have a vehicle) Such instances will get the default value “NOT EXIST” Case3: Attribute values are defined for the entity instance and the attribute instance should have a value (Student’s date of birth).

Guidelines:

Scenario:

Provide default values for each valid case of null values for the attribute in concern so that null values occur only for actually missing values which are invalid cases for the attribute in concern.

Case1: Attribute values that are not defined for a particular entity instance (e.g.: Maiden name of unmarried women ) Such instances will get the default value “NOT DEFINED”

Case2 : Attribute values that are defined for the entity instance whereas the real value for the attribute instance is null (eg: Vehicle number of a student who does not have a vehicle) Such instances will get the default value “NOT EXIST”

Case3: Attribute values are defined for the entity instance and the attribute instance should have a value (Student’s date of birth).

Validation Metric:

How mature is the creation and implementation of the DQ rules to define valid null cases

These are examples of how the characteristic might occur in a database.

Example:	Source:
Let us consider a Person relation with the attributes Name, Surname, BirthDate,and Email. The relation is shown in Figure 2.2. For the tuples with Id equalto2,3,and 4, the Email value is NULL. Let us suppose that the person represented by tuple 2 has no e-mail: no incompleteness case occurs. If the person represented by tuple 3 has an e-mail, but its value is not known then tuple 3 presents an incompleteness. Finally, if it is not known whether the person represented by tuple 4 has an e-mail or not, incompleteness may not be the case. ID 1 2 3 4 Name John Edward Anthony Marianne Surname Smith Monroe White Collins BirthDate 03/17/1974 02/03/1967 01/01/1936 11/20/1955 Email smith@abc.it NULL NULL NULL not existing existing but unknown not known if existing Fig. 2.2. The Person relation, with diﬀerent null value meanings for the e-mail attribute	C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006.
1) A database contains information on repairs done to capital equipment. How- ever, it is a known fact that sometimes the repairs are done and the informa- tion about the repair is just not entered into the database. This is the result of lack of concern on the part of the repair people and a lack of enforcement on the part of their supervisors. It is estimated that the amount of missing information is about 5%. This database is probably a good-quality database for assessing the genral health of capital equipment. Equipment that required a great deal of expense to maintain can be identiﬁed from the data. Unless the missing data is disproportionately skewed, the records are usable for all ordinary decisions. However, trying to use it as a base for evaluating information makes it a low-quality database. The missing transactions could easily tag an important piece of equipment as satisfying a warranty when in fact it does not. 2) A blank for COLLEGE_LAST_ATTENDED may be accurate or inaccurate. If the person it applied to had attended college, it would be inaccurate. This is another case of valid but not accurate.	J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

Example:

Source:

Let us consider a Person relation with the attributes Name, Surname,

BirthDate,and Email. The relation is shown in Figure 2.2. For the tuples with Id equalto2,3,and 4, the Email value is NULL. Let us suppose that the person represented by tuple 2 has no e-mail: no incompleteness case occurs. If the person represented by tuple 3 has an e-mail, but its value is not known then tuple 3 presents an incompleteness. Finally, if it is not known whether the person represented by tuple 4 has an e-mail or not, incompleteness may not be the case.

ID 1

2 3 4

Name John

Edward Anthony Marianne

Surname Smith

Monroe White Collins

BirthDate 03/17/1974 02/03/1967 01/01/1936 11/20/1955

smith@abc.it NULL NULL NULL

not existing existing but unknown not known if existing

Fig. 2.2. The Person relation, with diﬀerent null value meanings for the e-mail attribute

C. Batini and M, Scannapieco, “Data Quality: Concepts, Methodologies, and Techniques”, Springer, 2006.

1) A database contains information on repairs done to capital equipment. How- ever, it is a known fact that sometimes the repairs are done and the informa- tion about the repair is just not entered into the database. This is the result of lack of concern on the part of the repair people and a lack of enforcement on the part of their supervisors. It is estimated that the amount of missing information is about 5%. This database is probably a good-quality database for assessing the genral health of capital equipment. Equipment that required a great deal of expense to maintain can be identiﬁed from the data. Unless the missing data is disproportionately skewed, the records are usable for all ordinary decisions. However, trying to use it as a base for evaluating information makes it a low-quality database. The missing transactions could easily tag an important piece of equipment as satisfying a warranty when in fact it does not.

2) A blank for COLLEGE_LAST_ATTENDED may be accurate or inaccurate. If the person it applied to had attended college, it would be inaccurate. This is another case of valid but not accurate.

J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
1) A null value is a missing value. However, a value that is missing may provide more information than one might think because there may be different reason that it is missing. A null value might actually represent an unavailable value, an attribute that is not applicable for this entity, or no value in the attribute’s domain that correctly classifies this entity. Of course, the value may actually be missing. 2) When the null value (or absence of a value) is required for an attribute, there should be a recognizable form for presenting that null value that does not conflict with any valid values.	LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.
1) Ability to distinguish neatly (without ambiguities) null and default values from applicable values of the domain. 2) Completeness refers to the degree to which values are present in a data collection, as for as an individual datum is concerned, only two situations are possible: Either a value is assigned to the attribute in question or not. In the latter case, null, a special element of an attribute’s domain can be assigned as the attribute’s value. Depending on whether the attribute is mandatory, optional, or inapplicable, null can mean different things.	REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc.

Definition:

Source:

1) A null value is a missing value. However, a value that is missing may provide more information than one might think because there may be different reason that it is missing. A null value might actually represent an unavailable value, an attribute that is not applicable for this entity, or no value in the attribute’s domain that correctly classifies this entity. Of course, the value may actually be missing.

2) When the null value (or absence of a value) is required for an attribute, there should be a recognizable form for presenting that null value that does not conflict with any valid values.

LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.

1) Ability to distinguish neatly (without ambiguities) null and default values from applicable values of the domain.

2) Completeness refers to the degree to which values are present in a data collection, as for as an individual datum is concerned, only two situations are possible: Either a value is assigned to the attribute in question or not. In the latter case, null, a special element of an attribute’s domain can be assigned as the attribute’s value. Depending on whether the attribute is mandatory, optional, or inapplicable, null can mean different things.

REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc.

Accuracy to reference source

Characteristic Name:	Accuracy to reference source
Dimension:	Accuracy
Description:	Data should agree with an identified source
Granularity:	Element
Implementation Type:	Process-based approach
Characteristic Type:	Usage

Verification Metric:

The number of tasks failed or under performed due to lack of accuracy to reference sources

The number of complaints received due to lack of accuracy to reference sources

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines:	Scenario:
Establish the source for a data attribute and maintain facilities to access the correct source.	(1) Actual Cost of raw material is taken from Supplier invoices and not from quotation. (2) Interest rates are taken from daily central bank statistics which is available in the finance system online.
Establish the data capturing points in the business process without leading to any ambiguity and enforce process level validation mechanisms to ensure the process is being followed.	(1) Personal drug utilisation data is captured at POS units at pharmacies and ALL pharmacies in the country are connected to a central system (All pharmacy data is considered). (2) In a barcode scanning system in a production system, finished products cannot be scanned into quality checked products (Finished, Quality checked are the two data capturing points here)
Implement effective techniques and efficient technological solutions (devices) in collecting data which minimise data errors and omissions in data capturing.	(1) Barcode scanning is used to enter sales of products. (2) Invoices are scanned into the system and price is automatically recognised. (3) Standard forms are used to collect patient data.
If data is collected and transferred batch wise, establish the frequencies of data transfers/uploads considering the nature of the data and business needs.	(1) All drug utilisation data collected in the pharmacies are transferred to the central system at the end of every month. (2) Production efficiency data is transferred to monitoring systems every 30 minutes
Implement an effective and efficient data transferring technology which do not cause distortions or omissions to data	(1) Data migration tools
Define and implement appropriate input validation rules to notify the data collector/operator about the erroneous values being entered, avoid erroneous values being entered into database or erroneous values are flagged for clear identification	(1) Telephone number does not accept non numeric characters
Implement flexible data capturing interfaces to accommodate important but out of the way data.	(1) A field exists to record special comments in a goods receipts note (GRN)
Implement and enforce standardised data capturing procedures/ best practices through the system in collecting data.	(1) Standard wait times are used in taking blood samples of a patient. (e.g.: one hour after meal)
Establish mitigation mechanisms to handle measurement errors and ensure that acceptable error tolerance levels are established	(1) calibrate the equipments on a routine basis
Identify barriers for data collection or barriers for data providers and take appropriate actions to remove them	(1) Maintain a log file of response failures of a web based survey and then eliminate the root causes.
Identify the practices which encourage data providers	(1) Reward survey participants
Conduct regular training programs for data capturing/entering staff and educate them on possible data capturing problems and how to overcome data entry errors depending on the context	(1) Do not restart the Scanner when it is hung up while scanning (2) Repeat a telephone number in a different pattern to validate it from the source e.g. : 045 220 371 9 , in validating repeat it as 04 52 20 37 19

Validation Metric:

How mature is the process for ensuring accuracy for reference sources

These are examples of how the characteristic might occur in a database.

Example:	Source:
In this scenario, the parent, a US Citizen, applying to a European school completes the Date of Birth (D.O.B) on the application form in the US date format, MM/DD/YYYY rather than the European DD/MM/YYYY format, causing the representation of days and months to be reversed.	N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.
, let us consider two databases, say A and B, that contain the same data. If at time t a user updates data in database A and another user reads the same data from database B at time t' (t < t' ), the latter will read incorrect data. If t and f are included within the time interval between two subsequent data realignments	C. Cappiello, C. Francalanci, and B. Pernici, “Time-Related Factors of Data Quality in Multichannel Information System” in Journal of Management Information Systems, Vol. 20, No. 3, M.E. Sharpe, Inc., 2004, pp.71-91.
Consider an air traﬃc control center which receives data from several controller stations. To regulate air traﬃc, the traﬃc control center has to cope with uncertain data.Thus, the decision process must balance the delaying receiving more accurate data of airplane positions and the critical period of time in which an“eﬀective” decision must be made to regulate traﬃc;	B. Pernici, “Advanced Information Systems Engineering” in proc. The 22nd International Conference, CAiSE, Hammamet, Tunisia, June 2010.

Example:

Source:

In this scenario, the parent, a US Citizen, applying to a European school completes the Date of Birth (D.O.B) on the application form in the US date format, MM/DD/YYYY rather than the European DD/MM/YYYY format, causing the representation of days and months to be reversed.

N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

, let us consider two

databases, say A and B, that contain the same data. If at time t a user updates data in database A and another user reads the same data from database B at time t' (t < t' ), the latter will read incorrect data. If t and f are included within the time interval between two subsequent data realignments

C. Cappiello, C. Francalanci, and B. Pernici, “Time-Related Factors of Data Quality in Multichannel Information System” in Journal of Management Information Systems, Vol. 20, No. 3, M.E. Sharpe, Inc., 2004, pp.71-91.

Consider an air traﬃc control center which receives data from several controller stations. To regulate air traﬃc, the traﬃc control center has to cope with uncertain data.Thus, the decision process must balance the delaying receiving more accurate data of airplane positions and the critical period of time in which an“eﬀective” decision must be made to regulate traﬃc;

B. Pernici, “Advanced Information Systems Engineering” in proc. The 22nd International Conference, CAiSE, Hammamet, Tunisia, June 2010.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition:	Source:
A measure of the correctness of the content of the data (which requires an authoritative source of reference to be identified and accessible).	D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
The data agrees with an original, corroborative source record of data, such as a notarized birth certificate, document, or unaltered electronic data received from a party outside the control of the organization that is demonstrated to be a reliable source.	ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
1) Accuracy of data refers to how closely the data correctly captures what it was designed to capture. Verification of accuracy involves comparing the collected data to an external reference source that is known to be valid. Capturing data as close as possible to the point of activity contributes to accuracy. The need for accuracy must be balanced with the importance of the decisions that will be made based on the data and the cost and effort associated with data collection. If data accuracy is compromised in any way then this information should be made known to the data users. 2) Reliability of data refers to the extent to which data is collected consistently over time and by different organisations either manually or electronically.	HIQA 2011. International Review of Data Quality Health Information and Quality Authority (HIQA), Ireland. http://www.hiqa.ie/press-release/2011-04-28-international-review-data-quality.
Data accuracy refers to the degree with which data values agree with an identified source of correct information. There are different sources of correct information: database of record, a similar, corroborative set of data values from another table, dynamically computed values, the result of a manual workflow, or irate customers.	LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.
Data accuracy refers to the degree with which data correctly represents the “real-life” objects they are intended to model. In many cases, accuracy is measured by how the values agree with an identified source of correct information (such as reference data). There are different sources of correct information: a database of record, a similar corroborative set of data values from another table, dynamically computed values, or perhaps the result of a manual process.	LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation.
Accuracy of datum refers the nearness of the value v to some value v’ in the attribute domain, which is considered as the (or maybe only a) correct one for the entity e and the attribute a. In some cases, v’ is referred to as the standard. If the datum’s value v coincides value v’, the datum is said to be correct.	REDMAN, T. C. 1997. Data quality for the information age, Artech House, Inc.
Degree of correctness of a value when comparing with a reference one	STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.
The extent to which data are correct reliable and certified free of error.	WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.